DBM-6000 :
SIA Protocol Converter for GALAXY Central
This document is valid dor both DBM-6000 RS-485 and IP controllers. Interfacing
has been developped with a Galaxy G3 144 V5.0
The popular Galaxy central
can be monitored by the DBM-6000. All the zones and outputs status can be
monitored, and special commands can be sent via a dinTalk
program.
To interface one Galaxy
central to the DBM-6000, one Protocol Converter are needed.
A protocol converter can monitor up to 2000 points. This capacity is limited by
the number of DinCool channels in the controller.
Note: With previous
Galaxy versions, a GALAXY RS232 module was also needed. The GALAXY RS232 module
is a gateway with one RS-232 port to connect on the DINEC protocol
converter and one RS-485 port to connect on the GALAXY AB line.
1) How to
set up the system
- 2) Configuration of the
protocol converter
- 3) Configuration of a Galaxy
central
- 4) Configuration of the
messages
- 5) Configuration of the
detectors
- 6) Accessing variables with DinTalk
- 7) Connection control
- 8) Cabling
- 9) Status of the GALAXY Central
- 10) Screen examples for a
GALAXY 18
1) How to set up the system :
- Add a protocol converter on the
controller.
- In the window 'management of the devices
on the main bus", control that the model is "GALAXY
Interface" and the version is "3.30". If it is not the
case, then burn the converter flash with
the file named GALAXY_RS.s24 or GALAXY_IP.s24.
- Add one slave on the converter. Give it
the name GALAXY Central.
- Add the messages sets. Each message is destinated for a particular RIO. See below for
details.
- Add detectors in these messages.
- TIPS :
- To set up the system quickly and in a
safe way, start with one RIO, set it up completely and verify its correct
function. For the following RIO's, use all possibilities of COPY/INSERT
and COPY/PASTE on whole messages : it will create all the detectors for
you.
- To control and rename variables quickly,
use the 'list variables' options from the protocol converter or the
Galaxy icon submenu.
2) Configuration of the protocol converter:
|
Name |
GALAXY
Interface |
|
|
Address |
The exact
address number labelled on the protocol converter. 5333 is for example. |
|
|
Protocol |
Alarm
Central |
|
|
Bauds |
38400 |
This
is the default value for a Galaxy G3 |
|
Bits |
8 |
8 data
bits |
|
Parity |
None |
No parity |
|
Number Retry |
Internally fixed at 2 |
this is the number of times the message is repeated before the
converter generates a fault on the bus. |
Rx
Time out
|
2000 |
Do not change.
This is the time interval before repeating a message not acknowledged. |
|
Rx Time Ready |
Internally fixed 50 ms |
This is
the delay before sending the next message after an acknowledge. |
3) Configuration of a Galaxy central:
The Galaxy is a slave for
the protocol converter.
|
Name |
A
denomination for the Galaxy eg GALAXY 144 |
|
Address |
Don't
care |
|
Survey this connection |
Should
be checked, or no alarm bus error will be generated. |
The protocol parameters of
the Galaxy central are accessible via the menu
"INSTALLATOR 1" -> "COMMUNICATION" ->"RS232
EXT"
|
MODE |
DIRECT |
|
PROTOCOL/FORMAT |
SIA LEVEL
0 for a G3 |
|
IDENTIFICATION |
<BLANK> (use of default remote code) |
4) Configuration of the messages:
The Galaxy inputs/outputs
are grouped by messages. A message contains either the 8 zones or the 4 outputs
of the same RIO.
A protocol converter can drive up to 256 messages.
To indicates that this
message will read output status, increase the RIO address by 1000. See example.
|
Name |
The RIO
Name |
|
Address |
The RIO
Address (bus number+ value rotary switch) |
5) Configuration of the input/outputs
IN the DBM-6000, a zone or
an output is referred as a detector. The detectors must be put in the
normal order, starting with 1, without mixing. Latest detectors only can be ommited.
When you create the
detector (a Galaxy zone or an output), this window configuration is
automatically displayed. After, when editing the channel properties, go in the installator sheet and click on 'input properties' or select
the variable in the variable list of the Galaxy.
As for any other DinCool channel, you can set alarms. In case of alarm, it
is always immediate, the timer is not used.
|
Name |
a name |
|
Address |
The
number of the zone or relay ( 1 to 8) |
5.1 Configuring a zone:
|
|
States 0 to 3 only are meaningfull. Set the text as shown in the figure. At DBM-6000 side, the
temporisation is never used, in case of alarm in the central, the alarm in
the DBM is start immediately. The alarm profile can be put into auto
acknowledge if wished. On the 5.0
G3 we have, to reset the burglar alarm state sent by the Galaxy central, it
is necessary to disarm and to re-arm the central ! |
5.2 Configuring an output:
The
default plan images :
|
|
Not known |
|
|
Not in alarm |
|
|
Not used |
|
|
Alarm in the central |
|
|
Not used |
6) Accessing variables with DinTalk:
Add an external variable of
type integer. Select the wanted channel in the list.
For a zone, possible
integer value are:
|
0 |
Watch |
NO ALARM |
The input
is closed on a valid resistance (low, normal or high) |
|
1 |
Detection |
NO ALARM |
The input
is not closed on a valid resistance. (O/C, S/C or Open) |
|
2 |
Watch |
ALARM |
The input
is closed on a valid resistance (low, normal or high) |
|
3 |
Detection |
ALARM |
The input
is not closed on a valid resistance. (O/C, S/C or Open) |
For an output, possible integer
value are:
|
0 |
OFF |
The
output is ON |
|
1 |
ON |
The
Output is OFF |
Partitions
can be armed or disarmed by a PRINT command in DinTalk,
like in the following example:
DEFINE GLX_ARM_PART "CSA1*5"
DEFINE GLX_DIS_PART "CSA1*0"
Print 7 : GLX_ARM_PART
Print 7 : GLX_DIS_PART
Here ‘7’ is
the logical number of the protocol converter
‘CSA1*5’: to
arm group 1, ‘1’ is the group, ‘5’ is ‘Force set’
‘CSA1*0’: to
dis-arm group 1, ‘1’ is the group, ‘0’ is to ‘Unset’
See Galaxy
manual for the commands explanations
7) Connection
control:
Don't forget to set the
'Alarm on device offline' in the controller’s properties.
If the protocol converter is
disconnected, the converter detects the absence of communication and an error
bus is generated immediately. The alarm programmed for main bus errors (if any)
in the controller is started.
If the Galaxy RS-232 module
is disconnected from the converter, the converter detects the absence of
communication and an error bus is generated. The alarm programmed for main bus
errors (if any) in the controller is started.
If the Galaxy RS-232 module
is disconnected from the Galaxy bus, the converter detects the absence of
communication and an error bus is generated. The alarm programmed for main bus
errors (if any) in the controller is started.
8) Cabling RS-232
Galaxy G3/ Galaxy Dimension:
Wiring : RS232 cable: 3 wires
|
Galaxy |
Protocol converter (Modbus port) |
|
Rx |
Tx |
|
Tx |
Rx |
|
Gnd |
Gnd |
|
- |
Others:
not connected. |
Module RS232 (for older centrals):
Note : For the
GALAXY 500/512 with more than one bus, the RS-232 Module must be connected on
BUS 1.
Wiring : RS232 cable: 3 wires / Sub-D 25 Female:
|
Protocol converter (Modbus port) |
Sub D25 female |
|
Rx |
3 |
|
Tx |
2 |
|
Gnd |
5 |
|
- |
Others:
not connected. |
DIP-SWITCH for
38400 Bd, N, 8, 1:
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
|
OFF |
OFF |
OFF |
OFF |
OFF |
ON |
ON |
ON |
See also the cabling
diagrams in the general help of the DBM-6000.
9) Status of the GALAXY Central:
The status of the Galaxy
central can be monitored indirectly:
1) Affect some RIO's outputs
with the wanted status of the central. Using the Galaxy installator
1 menu options.
2) Read these outputs.
10) Screen examples for a GALAXY
18
|
|
|
